Value consistency

Characteristic Name:	Value consistency
Dimension:	Consistency
Description:	Data values are consistent and do not provide conflicting or heterogeneous instances
Granularity:	Element
Implementation Type:	Rule-based approach
Characteristic Type:	Declarative

Verification Metric:

The number of inconsistent data values reported in an attribute per thousand records

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines:	Scenario:
For critical data elements provide standard classifications (values lists) for data entry interfaces and restrict arbitrary values across the system	(1) Country, city are taken from a standard list. (2) Generally accepted industry classifications are used to analyse customers industry wise (Education, Banking & Finance, Medical, Manufacturing…….
When data elements are combined for specific identification/management/accounting purposes, standardise such combinations and use them across the system.	(1) Customer and sales order are combined for identification purposes (2) Costs of wastage are associated with individual orders they are incurred and managed.
Define data attributes in such a way that data values are atomic and hence consistency can be maintained for any form of aggregation or consolidation	Name is divided into first name Middle name and Last Name
Maintain consistency in using unit of measures across different tables and different data bases	Sales price is in $ in Sales table and Accounts receivable ledger

Validation Metric:

How mature is the creation and implementation of the DQ rules to maintain value consistency

These are examples of how the characteristic might occur in a database.

Example:	Source:
School admin: a student’s date of birth has the same value and format in the school register as that stored within the Student database.	N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.
For example, data are inconsistent when it is documented that a male patient has had a hysterectomy.	B. Cassidy, et al., “Practice Brief: Data Quality Management Model” in Journal of AHIMA, 1998, 69(6).
the name of the city and the postal code should be consistent. This can be enabled by entering just the postal code and ﬁlling in the name of the city systematically through the use of referential integrity with a postal code table	Y. Lee, et al., “Journey to Data Quality”, Massachusetts Institute of Technology, 2006.
the data values ST Louis and Saint Louis may both refer to the same city. However, the recordings are inconsistent, and thus at least one of them is inaccurate.	J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition:	Source:
Domain Level: The data values persist from a particular data element of the data source to another data element in a second data source. Consistency can also reflect the regular use of standardized values, articularly in descriptive elements. Entity Level: The entity’s domains and domain values either persist intact or can be logically linked from one data source to another data source. Consistency can also reflect the regular use of standardized values particularly in descriptive domains.	B. BYRNE, J. K., D. MCCARTY, G. SAUTER, H. SMITH, P WORCESTER 2008. The information perspective of SOA design Part 6:The value of applying the data quality analysis pattern in SOA. IBM corporation.
Determines the extent to which distinct data instances provide nonconflicting information about the same underlying data object. For example, the salary range for level 4 employees must be between $40,000 and $65,000.	G. GATLING, C. B., R. CHAMPLIN, H. STEFANI, G. WEIGEL 2007. Enterprise Information Management with SAP, Boston, Galileo Press Inc.
Data is consistent if it doesn’t convey heterogeneity, neither in contents nor in form – anti examples: Order.Payment. Type = ‘Check’; Order. Payment. CreditCard_Nr = 4252… (inconsistency in contents); Order.requested_by: ‘European Central Bank’;Order.delivered_to: ‘ECB’ (inconsistency in form,because in the first case the customer is identified by the full name, while in the second case the customer’s acronym is used).	KIMBALL, R. & CASERTA, J. 2004. The data warehouse ETL toolkit: practical techniques for extracting. Cleaning, Conforming, and Delivering, Digitized Format, originally published.
Consistency can be curiously simple or dangerously complex. In its most basic form, consistency refers to data values in one data set being consistent with values in another data set. Two data values drawn from separate data sets may be consistent with each other, yet both can be incorrect.	LOSHIN, D. 2001. Enterprise knowledge management: The data quality approach, Morgan Kaufmann Pub.
In its most basic form, consistency refers to data values in one data set being consistent with values in another data set. A strict definition of consistency specifies that two data values drawn from separate data sets must not conflict with each other, although consistency does not necessarily imply correctness.	LOSHIN, D. 2006. Monitoring Data quality Performance using Data Quality Metrics. Informatica Corporation.
Consistency, in popular usage, means that two or more things do not conflict with one another. This usage extends reasonably well to data values, although a bit of added discipline is desired.	REDMAN, T. C. 1997. Data quality for the information age, Artech House, Inc.

Ease of data access

Characteristic Name:	Ease of data access
Dimension:	Availability and Accessability
Description:	Data should be easily accessible in a form that is suitable for its intended use.
Granularity:	Information object
Implementation Type:	Process-based approach
Characteristic Type:	Usage

Verification Metric:

The number of tasks failed or under performed due to lack of ease in data access

The number of complaints received due to lack of ease in data access

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines:	Scenario:
Routinely accessed information to continue operations, should be automatically delivered to stakeholders online without wasting their time to search for it.	(1) Daily exchange rates are linked into the accounting application or maintained in a dash board on the accountants desktop. (2) Production efficiency is made available on a display board in the production floor.
Information needed for management reporting purposes should be identified and catered through built in reports where the users do not have to create the reports themselves.	(1) Order status is frequently searched information by different stake holder groups and hence a report is made available with multiple searching criteria.
Facilitate users by providing tools to query the database without using any specific technical knowledge and perform business analytics to bring innovation	(1) Technical infrastructure supports the users to develop their own reports based on dynamic information needs without consulting technical staff.
Facilitate the user to filter the relevant information depending on the need.	(1) Sales report with filtering criteria for customer and date range.
The interfaces and reports should be created conveniently the users do not have to write complex queries or further process information before usage.	(1) Product prices are ordered as per "Relevance" or "Price" to enable an e-commerce customer on a purchase decision

Validation Metric:

How mature is the process of maintaining ease in data access

These are examples of how the characteristic might occur in a database.

Example:	Source:
Consider a database containing orders from customers. A practice for handling complaints and returns is to create an “adjustment” order for backing out the original order and then writing a new order for the corrected information if applicable. This procedure assigns new order numbers to the adjustment and replacement orders. For the accounting department, this is a high-quality database. All of the numbers come out in the wash. For a business analyst trying to determine trends in growth of orders by region, this is a poor-quality database. If the business analyst assumes that each order number represents a distinct order, his analysis will be all wrong. Someone needs to explain the practice and the methods necessary to unravel the data to get to the real numbers (if that is even possible after the fact).	J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

Example:

Source:

Consider a database containing orders from customers. A practice for handling complaints and returns is to create an “adjustment” order for backing out the original order and then writing a new order for the corrected information if applicable. This procedure assigns new order numbers to the adjustment and replacement orders. For the accounting department, this is a high-quality database. All of the numbers come out in the wash. For a business analyst trying to determine trends in growth of orders by region, this is a poor-quality database. If the business analyst assumes that each order number represents a distinct order, his analysis will be all wrong. Someone needs to explain the practice and the methods necessary to unravel the data to get to the real numbers (if that is even possible after the fact).

J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition:	Source:
Accessibility refers to the physical conditions in which users can obtain data Clarity refers to the data’s information environment including appropriate metadata.	LYON, M. 2008. Assessing Data Quality , Monetary and Financial Statistics. Bank of England. http://www.bankofengland.co.uk/ statistics/Documents/ms/articles/art1mar08.pdf.
Speed and ease of locating and obtaining an information object relative to a particular activity	STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733.
Data are available or easily or quickly retrieved.	WANG, R. Y. & STRONG, D. M. 1996. Beyond accuracy: What data quality means to data consumers. Journal of management information systems, 5-33.